Management of media content playback

ABSTRACT

Example techniques may involve managing playback of media content by a playback device. In an example implementation, a playback device receives, via the network interface from a control device of the media playback system, an instruction to queue a container of audio tracks into a queue for playback by the playback device, wherein the container of audio tracks and consists of: (a) an album, (b) a playlist, or (c) an internet radio station. While the playback device is playing back the queue and before each audio track of the playlist is played back, the playback device determines whether the respective audio track is associated with a negative preference. If the respective audio track is associated with the negative preference, the playback device advances playback over the respective audio track to the next audio track within the queue.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. patent application Ser. No. 15/263,407, filed onSep. 13, 2016, entitled “Management of Media Content Playback,” thecontents of which are fully incorporated by reference herein in theirentirety. U.S. patent application Ser. No. 15/263,407 claims priorityunder 35 U.S.C. § 120 to, and is a continuation of, U.S. patentapplication Ser. No. 14/263,743, filed on Apr. 28, 2014, entitled“Management of Media Content Playback,” issued as U.S. Pat. No.9,478,247 on Oct. 25, 2016, the contents of which are fully incorporatedby reference herein in their entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other elementsdirected to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were severely limited until in 2003, when SONOS, Inc. filed forone of its first patent applications, entitled “Method for SynchronizingAudio Playback between Multiple Networked Devices,” and began offering amedia playback system for sale in 2005. The Sonos Wireless HiFi Systemenables people to experience music from virtually unlimited sources viaone or more networked playback devices. Through a software controlapplication installed on a smartphone, tablet, or computer, one can playwhat he or she wants in any room that has a networked playback device.Additionally, using the controller, for example, different songs can bestreamed to each room with a playback device, rooms can be groupedtogether for synchronous playback, or the same song can be heard in allrooms synchronously.

Given the ever growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example media playback system configuration in whichcertain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example controller interface;

FIG. 5 shows an example media playback environment;

FIG. 6A shows a first example flow diagram for managing playback ofmedia content;

FIG. 6B shows a second example flow diagram for managing playback ofmedia content;

FIG. 6C shows a third example flow diagram for managing playback ofmedia content;

FIG. 6D shows an example flow diagram for providing media content basedon media preferences of multiple user accounts; and

FIG. 7 shows aspects of an example media preference database.

The drawings are for the purpose of illustrating example embodiments,but it is understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Some embodiments described herein involve managing playback of mediacontent by a media playback system based on identified preference dataassociated with a user account interfacing with the media playbacksystem. In particular, the embodiments may involve preventing mediacontent from being played if the user account has a negative preferenceassociated with the media content.

In one example, a computing device, such as a media system serverassociated with a media playback system may store and maintain aplurality of user accounts associated with the media playback system.The computing device may then receive user data identifying which of theplurality of user accounts is interfacing with the media playback systemat a current time. For example, the user account may be interfacing withthe media playback system when the user account is being used to accessthe media playback system, when the user account is logged on to themedia playback system, and/or when a controller device associated withthe user account is in communicative range of the media playback system.In one case, the user data may indicate that users associated with someof the plurality of user accounts are within a physical proximity of themedia playback system, and consequently may experience media contentplayed by the media playback system.

The computing device may also receive media data identifying a mediaitem to be played by the media playback system. In one example, themedia item may be a music track provided by a service provider inresponse to an input via a first user account of the plurality of useraccounts. In one case, the service provider may provide the music trackbased on media preferences associated with the first user account. Inanother example, the music track may be part of a playlist provided bythe service provider according to a request via the first user account.In either case, the music track that is to be played may be provided atleast partially based on preferences associated with the first useraccount.

In one example, the user data may indicate that a second user account isinterfacing with the media playback system, and accordingly, one or moreusers associated with the second user account may be present where mediacontent is or will be played by the media playback system. Accordingly,media preferences associated with the second user account may also beconsidered when the media playback system is, or will be playing themusic track.

In particular, the computing device may identify, for at least thesecond user account, preference data associated with the media item. Themedia data may include metadata identifying the media item, and thecomputing device may use the metadata to identify preference dataassociated between the media item and the second user account. In oneexample, the preference data may be identified in a preference databaseassociated with the media playback system. The computing device may thendetermine whether the media item should be played based on theidentified preference data.

If the identified preference data indicates a negative preference, thecomputing device may determine the media item should not be played, andsend a transmission to the media playback system indicating that themedia item is not to be played. Alternatively, if the identifiedpreference data indicates a positive preference, or if no preference isidentified, the media playback system may proceed to play the mediaitem.

While the above examples refer to a first user account and a second useraccount, one having ordinary skill in the art will appreciate that theplurality of user accounts may include additional accounts, and thatpreferences associated with the additional accounts may also beidentified and considered when the media playback system plays mediacontent. In addition, while the above examples refer to actionsperformed by a computing device, such as a media system serverassociated with a media playback system, similar actions mayalternatively be performed at least in part, by one or more devices inthe media playback system. Other examples are also possible.

As indicated above, the examples provided herein involve managingplayback of media content by a media playback system based on identifiedpreference data associated with one of a plurality of user accountsinterfacing with the media playback system. In one embodiment, a methodis provided. The method involves maintaining, by a computing device, aplurality of user accounts associated with a media playback system, themedia playback system comprising at least one playback device,receiving, by the computing device, user data identifying which of theplurality of user accounts are currently interfacing with the mediaplayback system, receiving, by the computing device, media dataidentifying a media item to be played by the media playback system,identifying, by the computing device, for at least one of the pluralityof user accounts that are currently interfacing with the media playbacksystem, preference data associated with the media item, and determining,by the computing device, that the media item is not to be played by amedia playback system, based on the identified preference data.

In another embodiment, a device is provided. The device includes aprocessor, and memory having stored thereon instructions executable bythe processor to cause the device to perform functions. The functionsinclude maintaining a plurality of user accounts associated with a mediaplayback system, the media playback system comprising at least oneplayback device, receiving user data identifying which of the pluralityof user accounts are currently interfacing with the media playbacksystem, receiving media data identifying a media item to be played bythe media playback system, identifying for at least one of the pluralityof user accounts that are currently interfacing with the media playbacksystem, preference data associated with the media item, and determiningthat the media item is not to be played by a media playback system,based on the identified preference data.

In yet another embodiment, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include maintaining aplurality of user accounts associated with a media playback system, themedia playback system comprising at least one playback device, receivinguser data identifying which of the plurality of user accounts arecurrently interfacing with the media playback system, receiving mediadata identifying a media item to be played by the media playback system,identifying for at least one of the plurality of user accounts that arecurrently interfacing with the media playback system, preference dataassociated with the media item, and determining that the media item isnot to be played by a media playback system, based on the identifiedpreference data.

It will be understood by one of ordinary skill in the art that thisdisclosure includes numerous other embodiments.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 inwhich one or more embodiments disclosed herein may be practiced orimplemented. The media playback system 100 as shown is associated withan example home environment having several rooms and spaces, such as forexample, a master bedroom, an office, a dining room, and a living room.As shown in the example of FIG. 1, the media playback system 100includes playback devices 102-124, control devices 126 and 128, and awired or wireless network router 130.

Further discussions relating to the different components of the examplemedia playback system 100 and how the different components may interactto provide a user with a media experience may be found in the followingsections. While discussions herein may generally refer to the examplemedia playback system 100, technologies described herein are not limitedto applications within, among other things, the home environment asshown in FIG. 1. For instance, the technologies described herein may beuseful in environments where multi-zone audio may be desired, such as,for example, a commercial setting like a restaurant, mall or airport, avehicle like a sports utility vehicle (SUV), bus or car, a ship or boat,an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device200 that may be configured to be one or more of the playback devices102-124 of the media playback system 100 of FIG. 1. The playback device200 may include a processor 202, software components 204, memory 206,audio processing components 208, audio amplifier(s) 210, speaker(s) 212,and a network interface 214 including wireless interface(s) 216 andwired interface(s) 218. In one case, the playback device 200 may notinclude the speaker(s) 212, but rather a speaker interface forconnecting the playback device 200 to external speakers. In anothercase, the playback device 200 may include neither the speaker(s) 212 northe audio amplifier(s) 210, but rather an audio interface for connectingthe playback device 200 to an external audio amplifier or audio-visualreceiver.

In one example, the processor 202 may be a clock-driven computingcomponent configured to process input data according to instructionsstored in the memory 206. The memory 206 may be a tangiblecomputer-readable medium configured to store instructions executable bythe processor 202. For instance, the memory 206 may be data storage thatcan be loaded with one or more of the software components 204 executableby the processor 202 to achieve certain functions. In one example, thefunctions may involve the playback device 200 retrieving audio data froman audio source or another playback device. In another example, thefunctions may involve the playback device 200 sending audio data toanother device or playback device on a network. In yet another example,the functions may involve pairing of the playback device 200 with one ormore playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizingplayback of audio content with one or more other playback devices.During synchronous playback, a listener will preferably not be able toperceive time-delay differences between playback of the audio content bythe playback device 200 and the one or more other playback devices. U.S.Pat. No. 8,234,395 entitled, “System and method for synchronizingoperations among a plurality of independently clocked digital dataprocessing devices,” which is hereby incorporated by reference, providesin more detail some examples for audio playback synchronization amongplayback devices.

The memory 206 may further be configured to store data associated withthe playback device 200, such as one or more zones and/or zone groupsthe playback device 200 is a part of, audio sources accessible by theplayback device 200, or a playback queue that the playback device 200(or some other playback device) may be associated with. The data may bestored as one or more state variables that are periodically updated andused to describe the state of the playback device 200. The memory 206may also include the data associated with the state of the other devicesof the media system, and shared from time to time among the devices sothat one or more of the devices have the most recent data associatedwith the system. Other embodiments are also possible.

The audio processing components 208 may include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor (DSP), and soon. In one embodiment, one or more of the audio processing components208 may be a subcomponent of the processor 202. In one example, audiocontent may be processed and/or intentionally altered by the audioprocessing components 208 to produce audio signals. The produced audiosignals may then be provided to the audio amplifier(s) 210 foramplification and playback through speaker(s) 212. Particularly, theaudio amplifier(s) 210 may include devices configured to amplify audiosignals to a level for driving one or more of the speakers 212. Thespeaker(s) 212 may include an individual transducer (e.g., a “driver”)or a complete speaker system involving an enclosure with one or moredrivers. A particular driver of the speaker(s) 212 may include, forexample, a subwoofer (e.g., for low frequencies), a mid-range driver(e.g., for middle frequencies), and/or a tweeter (e.g., for highfrequencies). In some cases, each transducer in the one or more speakers212 may be driven by an individual corresponding audio amplifier of theaudio amplifier(s) 210. In addition to producing analog signals forplayback by the playback device 200, the audio processing components 208may be configured to process audio content to be sent to one or moreother playback devices for playback.

Audio content to be processed and/or played back by the playback device200 may be received from an external source, such as via an audioline-in input connection (e.g., an auto-detecting 3.5 mm audio line-inconnection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flowbetween the playback device 200 and one or more other devices on a datanetwork. As such, the playback device 200 may be configured to receiveaudio content over the data network from one or more other playbackdevices in communication with the playback device 200, network deviceswithin a local area network, or audio content sources over a wide areanetwork such as the Internet. In one example, the audio content andother signals transmitted and received by the playback device 200 may betransmitted in the form of digital packet data containing an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 214 may be configured to parse thedigital packet data such that the data destined for the playback device200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s)216 and wired interface(s) 218. The wireless interface(s) 216 mayprovide network interface functions for the playback device 200 towirelessly communicate with other devices (e.g., other playbackdevice(s), speaker(s), receiver(s), network device(s), control device(s)within a data network the playback device 200 is associated with) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4Gmobile communication standard, and so on). The wired interface(s) 218may provide network interface functions for the playback device 200 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 802.3). While the networkinterface 214 shown in FIG. 2 includes both wireless interface(s) 216and wired interface(s) 218, the network interface 214 may in someembodiments include only wireless interface(s) or only wiredinterface(s).

In one example, the playback device 200 and one other playback devicemay be paired to play two separate audio components of audio content.For instance, playback device 200 may be configured to play a leftchannel audio component, while the other playback device may beconfigured to play a right channel audio component, thereby producing orenhancing a stereo effect of the audio content. The paired playbackdevices (also referred to as “bonded playback devices”) may further playaudio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonicallyconsolidated with one or more other playback devices to form a single,consolidated playback device. A consolidated playback device may beconfigured to process and reproduce sound differently than anunconsolidated playback device or playback devices that are paired,because a consolidated playback device may have additional speakerdrivers through which audio content may be rendered. For instance, ifthe playback device 200 is a playback device designed to render lowfrequency range audio content (i.e. a subwoofer), the playback device200 may be consolidated with a playback device designed to render fullfrequency range audio content. In such a case, the full frequency rangeplayback device, when consolidated with the low frequency playbackdevice 200, may be configured to render only the mid and high frequencycomponents of audio content, while the low frequency range playbackdevice 200 renders the low frequency component of the audio content. Theconsolidated playback device may further be paired with a singleplayback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered)for sale certain playback devices including a “PLAY:1,” “PLAY:3,”“PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any otherpast, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it is understood that aplayback device is not limited to the example illustrated in FIG. 2 orto the SONOS product offerings. For example, a playback device mayinclude a wired or wireless headphone. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, theenvironment may have one or more playback zones, each with one or moreplayback devices. The media playback system 100 may be established withone or more playback zones, after which one or more zones may be added,or removed to arrive at the example configuration shown in FIG. 1. Eachzone may be given a name according to a different room or space such asan office, bathroom, master bedroom, bedroom, kitchen, dining room,living room, and/or balcony. In one case, a single playback zone mayinclude multiple rooms or spaces. In another case, a single room orspace may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office,and bedroom zones each have one playback device, while the living roomand master bedroom zones each have multiple playback devices. In theliving room zone, playback devices 104, 106, 108, and 110 may beconfigured to play audio content in synchrony as individual playbackdevices, as one or more bonded playback devices, as one or moreconsolidated playback devices, or any combination thereof. Similarly, inthe case of the master bedroom, playback devices 122 and 124 may beconfigured to play audio content in synchrony as individual playbackdevices, as a bonded playback device, or as a consolidated playbackdevice.

In one example, one or more playback zones in the environment of FIG. 1may each be playing different audio content. For instance, the user maybe grilling in the balcony zone and listening to hip hop music beingplayed by the playback device 102 while another user may be preparingfood in the kitchen zone and listening to classical music being playedby the playback device 114. In another example, a playback zone may playthe same audio content in synchrony with another playback zone. Forinstance, the user may be in the office zone where the playback device118 is playing the same rock music that is being playing by playbackdevice 102 in the balcony zone. In such a case, playback devices 102 and118 may be playing the rock music in synchrony such that the user mayseamlessly (or at least substantially seamlessly) enjoy the audiocontent that is being played out-loud while moving between differentplayback zones. Synchronization among playback zones may be achieved ina manner similar to that of synchronization among playback devices, asdescribed in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system100 may be dynamically modified, and in some embodiments, the mediaplayback system 100 supports numerous configurations. For instance, if auser physically moves one or more playback devices to or from a zone,the media playback system 100 may be reconfigured to accommodate thechange(s). For instance, if the user physically moves the playbackdevice 102 from the balcony zone to the office zone, the office zone maynow include both the playback device 118 and the playback device 102.The playback device 102 may be paired or grouped with the office zoneand/or renamed if so desired via a control device such as the controldevices 126 and 128. On the other hand, if the one or more playbackdevices are moved to a particular area in the home environment that isnot already a playback zone, a new playback zone may be created for theparticular area.

Further, different playback zones of the media playback system 100 maybe dynamically combined into zone groups or split up into individualplayback zones. For instance, the dining room zone and the kitchen zone114 may be combined into a zone group for a dinner party such thatplayback devices 112 and 114 may render audio content in synchrony. Onthe other hand, the living room zone may be split into a television zoneincluding playback device 104, and a listening zone including playbackdevices 106, 108, and 110, if the user wishes to listen to music in theliving room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300that may be configured to be one or both of the control devices 126 and128 of the media playback system 100. As shown, the control device 300may include a processor 302, memory 304, a network interface 306, and auser interface 308. In one example, the control device 300 may be adedicated controller for the media playback system 100. In anotherexample, the control device 300 may be a network device on which mediaplayback system controller application software may be installed, suchas for example, an iPhone™ iPad™ or any other smart phone, tablet ornetwork device (e.g., a networked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant tofacilitating user access, control, and configuration of the mediaplayback system 100. The memory 304 may be configured to storeinstructions executable by the processor 302 to perform those functions.The memory 304 may also be configured to store the media playback systemcontroller application software and other data associated with the mediaplayback system 100 and the user.

In one example, the network interface 306 may be based on an industrystandard (e.g., infrared, radio, wired standards including IEEE 802.3,wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n,802.11ac, 802.15, 4G mobile communication standard, and so on). Thenetwork interface 306 may provide a means for the control device 300 tocommunicate with other devices in the media playback system 100. In oneexample, data and information (e.g., such as a state variable) may becommunicated between control device 300 and other devices via thenetwork interface 306. For instance, playback zone and zone groupconfigurations in the media playback system 100 may be received by thecontrol device 300 from a playback device or another network device, ortransmitted by the control device 300 to another playback device ornetwork device via the network interface 306. In some cases, the othernetwork device may be another control device.

Playback device control commands such as volume control and audioplayback control may also be communicated from the control device 300 toa playback device via the network interface 306. As suggested above,changes to configurations of the media playback system 100 may also beperformed by a user using the control device 300. The configurationchanges may include adding/removing one or more playback devices to/froma zone, adding/removing one or more zones to/from a zone group, forminga bonded or consolidated player, separating one or more playback devicesfrom a bonded or consolidated player, among others. Accordingly, thecontrol device 300 may sometimes be referred to as a controller, whetherthe control device 300 is a dedicated controller or a network device onwhich media playback system controller application software isinstalled.

The user interface 308 of the control device 300 may be configured tofacilitate user access and control of the media playback system 100, byproviding a controller interface such as the controller interface 400shown in FIG. 4. The controller interface 400 includes a playbackcontrol region 410, a playback zone region 420, a playback status region430, a playback queue region 440, and an audio content sources region450. The user interface 400 as shown is just one example of a userinterface that may be provided on a network device such as the controldevice 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1)and accessed by users to control a media playback system such as themedia playback system 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 410 may include selectable (e.g., by way oftouch or by using a cursor) icons to cause playback devices in aselected playback zone or zone group to play or pause, fast forward,rewind, skip to next, skip to previous, enter/exit shuffle mode,enter/exit repeat mode, enter/exit cross fade mode. The playback controlregion 410 may also include selectable icons to modify equalizationsettings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playbackzones within the media playback system 100. In some embodiments, thegraphical representations of playback zones may be selectable to bringup additional selectable icons to manage or configure the playback zonesin the media playback system, such as a creation of bonded zones,creation of zone groups, separation of zone groups, and renaming of zonegroups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the mediaplayback system to be grouped with the particular zone. Once grouped,playback devices in the zones that have been grouped with the particularzone will be configured to play audio content in synchrony with theplayback device(s) in the particular zone. Analogously, a “group” iconmay be provided within a graphical representation of a zone group. Inthis case, the “group” icon may be selectable to bring up options todeselect one or more zones in the zone group to be removed from the zonegroup. Other interactions and implementations for grouping andungrouping zones via a user interface such as the user interface 400 arealso possible. The representations of playback zones in the playbackzone region 420 may be dynamically updated as playback zone or zonegroup configurations are modified.

The playback status region 430 may include graphical representations ofaudio content that is presently being played, previously played, orscheduled to play next in the selected playback zone or zone group. Theselected playback zone or zone group may be visually distinguished onthe user interface, such as within the playback zone region 420 and/orthe playback status region 430. The graphical representations mayinclude track title, artist name, album name, album year, track length,and other relevant information that may be useful for the user to knowwhen controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue containing informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL) or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streaming audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue, or beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue, or be associated with a new playback queue thatis empty, or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphicalrepresentations of audio content in the playback queue region 440 mayinclude track titles, artist names, track lengths, and other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device.

The audio content sources region 450 may include graphicalrepresentations of selectable audio content sources from which audiocontent may be retrieved and played by the selected playback zone orzone group. Discussions pertaining to audio content sources may be foundin the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zonegroup may be configured to retrieve for playback audio content (e.g.according to a corresponding URI or URL for the audio content) from avariety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the media playbacksystem 100 of FIG. 1, local music libraries on one or more networkdevices (such as a control device, a network-enabled personal computer,or a networked-attached storage (NAS), for example), streaming audioservices providing audio content via the Internet (e.g., the cloud), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network devise, among otherpossibilities.

In some embodiments, audio content sources may be regularly added orremoved from a media playback system such as the media playback system100 of FIG. 1. In one example, an indexing of audio items may beperformed whenever one or more audio content sources are added, removedor updated. Indexing of audio items may involve scanning foridentifiable audio items in all folders/directory shared over a networkaccessible by playback devices in the media playback system, andgenerating or updating an audio content database containing metadata(e.g., title, artist, album, track length, among others) and otherassociated information, such as a URI or URL for each identifiable audioitem found. Other examples for managing and maintaining audio contentsources may also be possible.

The above discussions relating to playback devices, controller devices,playback zone configurations, and media content sources provide onlysome examples of operating environments within which functions andmethods described below may be implemented. Other operating environmentsand configurations of media playback systems, playback devices, andnetwork devices not explicitly described herein may also be applicableand suitable for implementation of the functions and methods.

III. Example Methods for Managing Playback of Media Content

As discussed above, embodiments described herein may involve managingplayback of media by a media playback system based on identifiedpreference data associated with user accounts interfacing with the mediaplayback system. FIG. 500 shows an example media playback systemenvironment 500 within which the embodiments may be implemented. Asshown, the media playback system environment 500 includes an exampleservice provider 502, an example media system server 504, an examplemedia playback system 506, an example first user account 508, and anexample second user account 510. The first user account 508 and thesecond user account 510 may be two of a plurality of user accounts foraccessing the media playback system 506 and/or the service provider 502.As such, one or more controller devices, such as the control device 300of FIG. 3, may communicate with the media playback system 506 and/or theservice provider 502 (and other service providers) using the first useraccount 508 and/or the second user account 510. Each of the serviceprovider 502, media system server 504, media playback system 506, andany controller device(s) associated with the first user account 508 orthe second user account 510 may communicate with each other eitherdirectly, or indirectly via another device, over a local area network(LAN), wide area network (WAN) or some combination thereof.

The media playback system 506 may be a playback system such as thatdescribed above in connection to FIG. 1, and may include one or moreplayback devices configured to play media content in synchrony withinone or more playback zones. As indicated above, the first user account508 and the second user account 510 may be used to utilize the mediaplayback system 506.

The media system server 504 may be a server associated with the mediaplayback system 506, and may store information relating to the mediaplayback system 506. Such information may include playback deviceinformation, playback zone information, service provider associationinformation, and/or user account information, among other information.

The service provider 502 may provide media content for playback by themedia playback system 506. In one example, the service provider 502 maybe a media streaming service. The content provided by the serviceprovider 502 may include individual media items or collections of mediaitems (i.e. albums, playlists, radio channels, etc.). The serviceprovider 502 may provide media content in response to specific requestsfor explicitly chosen media items, (i.e. requests for specific tracks,albums, etc), or requests for certain types of media content (i.e. acatered playlist, radio channels, etc). The service provider 502 mayalso provide catered playlists of media content based on userpreferences and input. For instance, if a service provider user accountfor the service provider 502 indicates that the user enjoys a particulargenre of music, the service provider 502 may provide music within theparticular genre, or music within similar, or related genres. Otherexamples of services that may be available through service provider 502are also possible.

In one example, the first user account 508 may be used to request mediacontent from the service provider 502. As such, the service provider 502may provide media content for playback by the media playback system 506based on media preferences associated with the first user account 508,and/or according to requests from the first user account 508. In somecases, however, the service provider 502 may provide media content thathas a negative preference associated with the second user account 510while users associated with the second user account 510 are presentwhere the music is, or will be playing. Embodiments described herein maybe implemented for managing playback of media content based at leastpartially on media preference associated with the second user account510, even when the media content is provided in response to a requestvia the first user account 508.

FIG. 6A shows an example flow diagram of an example method 600 for suchan embodiment. Method 600 shown in FIG. 6A presents an embodiment of amethod that can be implemented within an operating environmentinvolving, for example, the media playback system 100 of FIG. 1, one ormore of the playback device 200 of FIG. 2, one or more of the controldevice 300 of FIG. 3, and the media playback system environment 500 ofFIG. 5. In other words, the method 600 may be performed by any one ormore of the devices, systems, and servers described above. In oneexample, the functions of the embodiments as discussed herein areperformed by the media system server 504. In another example, thefunctions may alternatively be performed by one or more devices in themedia playback system 506. In a further example, the functions may beperformed in part by the media system server 504 and in part by one ormore devices in the media playback system 506. Other examples are alsopossible.

Method 600 may include one or more operations, functions, or actions asillustrated by one or more of blocks 602-612. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon the desired implementation.

In addition, for the method 600 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 600 and other processes and methods disclosedherein, each block in FIG. 6A may represent circuitry that is wired toperform the specific logical functions in the process.

At block 602, the method 600 involves maintaining a plurality of useraccounts associated with a media playback system. In one example, themedia system server 504 may store a database containing user accountinformation for the plurality of user accounts associated with the mediaplayback system 506. Each of the user accounts may be used to access themedia playback system 506. For instance, a user may log on to the mediaplayback system 506 using one of the plurality of user accounts. Assuggested above, the plurality of user accounts associated with themedia playback system may include the first user account 508 and thesecond user account 510.

At block 604, the method 600 involves receiving user data identifyingwhich of the plurality of user accounts are currently interfacing withthe media playback system. In one example, a user account may beconsidered to be interfacing with the media playback system if the useraccount is logged on the media playback system 506, actively interactingwith the media playback system, and/or tied to a controller device incommunication with the media playback system. In one case, mediaplayback system 506 may provide the media system server 504 with userdata identifying currently interfacing user accounts. The media playbacksystem 506 may provide this information periodically, whenever a useraccount becomes active/not active, or whenever it is about to play amedia item. In another example, the media system server 504 mayperiodically send to the media playback system 506, a request for acurrent/updated user data. In response, the media playback system 506may identify which user accounts are currently interfacing with themedia playback system 506, and send to the media system server 504, theuser data identifying the currently interfacing user accounts.

In another case, the media system server 504 may send the request forthe current/updated user data when such information is needed. Forinstance, the media system server 504 may send the request whendetermining whether media content is to be played by the media playbacksystem 506 based at least partially on actively interfacing useraccounts. As such, in some embodiments, block 604 may be implementedafter block 606, which is discussed below.

At block 606, the method 600 involves receiving media data identifying amedia item to be played by the media playback system. In one example,the service provider 502 may provide the media item to the mediaplayback system 506 for playback. Then, based on the received mediaitem, the media playback system 506 may send the media data identifyingthe media item to the media system server 504. In another example, theserver provider 502 may send the media data directly to the media systemserver 504 prior to, or concurrently with providing the media item tothe media playback system 506 for playback. Other examples are alsopossible.

In one example, the media item may be provided by the service provider502 in response to an input received via the first user account. In sucha case, the media item may have been selected by the service provider502 based on media preferences associated with the first user account508.

The media data may include metadata identifying the media item. Forinstance, the metadata may indicate one or more of a track title, artistname, album name, genre, or contextual information such as a time ofday, season, or activity the media item may be associated with orsuitable for, among others. In some cases, the metadata may furtherindicate a service-provider identifier used by the service provider 502to identify the media item.

At block 608, the method 600 involves identifying, for at least one ofthe plurality of user accounts that are currently interfacing with themedia playback system, preference data associated with the media item.Continuing with the examples above, if the user data indicates that thefirst user account 508 and the second user account 510 are currentlyinterfacing the media playback system 506, preference data associatedbetween the media item and the first user account 508, and preferencedata associated between the media item and the second user account 510may both be identified. Preference data associated between the mediaitem and any other user accounts currently interfacing the mediaplayback system 506 may also be identified.

For illustration purposes, the following discussion of preference dataidentification at block 608 may generally involve identifying preferencedata associated between the media item and the second user account 510.One having ordinary skill in the art will appreciate that the relevantdescriptions and examples may also be applied to any other user accountsidentified in the user data as currently interfacing the media playbacksystem 506.

In one example, if the second user account 510 is associated with one ormore service providers including the service provider 502, thepreference data may be identified by querying one or more of the serviceproviders for any media preferences associated with the media item anduser accounts that are currently interfacing the media playback system506. In another example, the preference data may be identified in apreference database that is affiliated with the media playback system506. The preference database may contain preference data associatedbetween media items and user accounts associated with the media playbacksystem 506. As such, the preference database may include preference dataindicating preferences associated with at least the first user account508 and the second user account 510.

FIG. 7 shows aspects of an example preference database 700 that mayinclude information associated with the media playback system 506. Inone example, the preference database 700 may be stored on one or moreremote servers, such as the media system server 504. In another example,the preference database may be stored on one or more local devices incommunication with the media playback system 506. In a further example,parts of the preference database may be stored on the one or more remoteservers and the one or more local devices. Other examples are alsopossible.

As shown, the preference database 700 includes columns for dataidentifying a media item, including a track ID column, a track artistcolumn, and a track album column. For each media item entry, preferencedata associated with the media item entry is shown in a preferencecolumn. In this example, a “+” in the preference column may indicate apositive preference for the respective entry, and a “−” in thepreference column may indicate a negative preference for the respectiveentry. In some cases, the format of the preference data mayalternatively be on a gradient scale, rather than a binary scale. Forinstance, a preference may range from one to five.

Further, a user account associated with a media item entry may beprovided in a user account column. In this illustrative example, a useraccount of “User1” may indicate that the respective media item entriesand preference data are associated with the first user account 508, anda user account of “User2” may indicate that the respective media itementries and preference data are associated with the second user account510.

One having ordinary skill in the art will appreciate that the preferencedatabase 700 and the entries shown in FIG. 7 are for illustrationpurposes only and should not be considered limiting, as other databaseformats for storing preference data are also possible. For instance,additional columns for information associated with the media itementries, preferences, or user accounts may also be included. Otherexamples are also possible.

Referring back to block 608, identifying preference data associated withthe media item may involve searching the preference database for a mediaitem entry that is associated with the user accounts currentlyinterfacing the media playback system 506, and that is related to themedia item. Preference data corresponding to the media item entry maythen be identified as being associated with the media item.

The searching may be based on the metadata identifying the media item.In one example, referring to FIG. 7, if the metadata identifying themedia item indicates a track ID of “Track5” and a track artist name of“Artist2,” preference data for a media item entry having a user accountof User2 (for the second user account 510) and matching track title andartist name, may be identified in the preference database. As shown inthe preference database 700, preference data indicating a negativepreference may be identified as being associated with the second useraccount 510 and the media item entry having the track ID of Track5 andthe track artist of Artist2.

In some cases, the search for database entries in the preferencedatabase may be implemented such that exact matches are required. Forinstance, if the received metadata indicates a different album name than“Album3” as shown in FIG. 7, then the preference associated with Track5and Artist2 may not be identified as relevant to the media item.

In some other cases, the search for database entries in the preferencedatabase 700 may be implemented according to an approximate stringmatching (or “fuzzy matching”). In such a case, if the received metadataindicates a different album name than Album3 for Track5 and Artist2, thepreference data associated with the media item entry in the preferencedatabase 700 having a track title of Track5 and an artist name ofArtist2 may still be recognized as being applicable to the media item.

In some other cases, the identified preference data may be associatedwith media content similar to the media item, and thus indirectlyassociated with the particular media item. For instance, the metadatafor the media item may indicate a track artist of the media item. Inthis case, preference data corresponding to media item entries havingthe track artist may be identified for the media item. Otherimplementations of database searching, including combinations of theexamples discussed above are also possible.

In one example, the second user account 510 may further, oralternatively, be a user account used to access another media playbacksystem. In such a case, a different preference database affiliated withthe other media playback system may also contain preference dataassociated with the second user account 510. Accordingly, identifyingthe preference associated with the second user account 510 may involvesearching in the different preference database for media item entriesassociated with the media item and the second user account 510. In oneexample, the other media playback system may be similar to the mediaplayback system 506. In some cases, the different preference databasemay be of a similar format as the preference database 700. In one case,the different preference database may be stored on the media systemserver 540 along with the preference database 700. Other examples arealso possible.

Referring back to the method 600, block 610 involves determining, basedon the identified preference data, whether the media item should beplayed. In one case, the identified preference data may indicate asimple positive preference or negative preference. In another case, theidentified preference data may indicate multiple preferences that aregenerally positive or negative. In either case, if the identifiedpreference data indicates a clearly positive preference, a determinationmay be made that the media item should be played. On the other hand, ifthe identified preference data indicates a clearly negative preference,a determination may be made that the media item should not be played.

In some other cases, the identified preference data may indicatemultiple preferences, including both positive and negative preferences.For instance, the preference data may indicate preferences from multipleuser accounts that are currently interfacing the media playback system506. In such cases, a determination may be made based on the differentpreferences. In one example, the different preferences may be weighteddifferently based on their respective associations between the mediaitem (i.e. how close of a match between the corresponding media itementry and the media item), and a determination of whether the media itemshould be played may be based on an average or sum of the weightedpreferences. In such a case, a preference threshold may be implementedsuch that a determination is made that the media item should be playedonly if the average or sum of the weighted preferences exceeds thethreshold. Other examples are also possible.

As shown in FIG. 6, if at block 610, a determination is made that themedia item should be played, the media playback system 506 may in oneexample, proceed to play the media item. Alternatively, in someembodiments, a transmission indicating that the media item is to beplayed may be sent to one or more playback devices in the media playbacksystem 506. In some cases, if the media item is provided to the one ormore playback devices from the service provider 502 via the media systemserver 504, or another device in the media playback system 506, atransmission or forwarding of the media item to the one or more playbackdevices in the media playback system 506 may indicate that the mediaitem is to be played.

Alternatively, if a determination is made that the media item should notto be played, the method 600 may proceed to block 612, which involvessending a transmission indicating that the media item is not to beplayed. In one example, the transmission may inform the one or moreplayback devices in the media playback system 506 that the media itemwill not be provided because a determination is made that the media itemshould not be played.

In one example, the media system server 504 may directly send thetransmission to the service provider 502. In another example, the mediaplayback system 506, upon receiving the transmission, may send thetransmission to the service provider 502. In one case, the mediaplayback system 506 may also send a request for different media content.In another example, the media playback system 506 may also send to theservice provider 502, preference data indicating a negative preferenceassociated between the media item that is not to be played and thesecond user account 510. In this case, if the second user account 510 isan account used to access the service provider 502, the service provider502 may record the negative preference for the media item in associationwith the second user account 510. Other examples are also possible.

In some embodiments, a transmission may also be sent to one or morecontroller devices in communication with the media playback system 506.The respective user interfaces of the one or more controller devices mayaccordingly display an indication that a media item was not played basedon an identified preference. In some cases, the indication may identifythe media item that was not played.

In the examples discussed above, the media system server 504 maycommunicate directly with both the media playback system 506 and theservice provider 502. In some cases, however, the service provider 502may be configured to communicate directly with the media playback system506, and not configured to communicate directly with the media system504. As such, the media system server 504 may communicate with theservice provider 502 via the media playback system 506. FIG. 6B shows anexample flow diagram of a method 650 for an embodiment in which themedia playback system 506 provides communication between the mediasystem server 504 and the service provider 502.

Method 650 shown in FIG. 6B presents an embodiment of a method that canbe implemented within an operating environment involving, for example,the media playback system 100 of FIG. 1, one or more of the playbackdevice 200 of FIG. 2, one or more of the control device 300 of FIG. 3,and the media playback system environment 500 of FIG. 5. In other words,the method 600 may be performed by any one or more of the devices,systems, and servers described above. Method 650 may include one or moreoperations, functions, or actions as illustrated by one or more ofblocks 652-658. Although the blocks are illustrated in sequential order,these blocks may also be performed in parallel, and/or in a differentorder than those described herein. Also, the various blocks may becombined into fewer blocks, divided into additional blocks, and/orremoved based upon the desired implementation.

At block 652, the method 650 involves receiving from a service provider,data indicating a first media item to be played. In one example, adevice, such as a playback device in the media playback system 506 maygenerally be configured to receive, from the service provider 502, mediacontent to be played by the playback device and/or other playbackdevices in the media playback system 506. The first media item may bethe media item received from the service provider 502 in response to aninput from a user of the media playback system 506, as discussedpreviously in connection to FIG. 6A.

At block 654, the method 650 involves sending to a computing device,media data identifying the first media item that is to be played.Continuing with the examples above, the computing device may be themedia system server 504. In one example, the service provider 502, whenproviding the first media item to the playback device for playback, mayalso provide metadata associated with the first media item. In somecases, some or all of the metadata may be displayed on a controllerinterface for the media playback system 506 if and when the first mediaitem is played by the playback device. In one case, the playback devicemay send to the media system server 504, media data containing the someor all of the metadata identifying the first media item.

At block 656, the method 650 involves receiving from the computingdevice, a transmission indicating that the first media item is not to beplayed. In one example, the media system server 504 may determinewhether the first media item is to be played, and send a transmission tothe media playback system 506, as discussed above with respect to method600 shown in FIG. 6A. At block 656 of method 650, the media playbacksystem 506 may receive the transmission indicating that the media itemis not to be played, and accordingly, does not play the media item. Inone example, the media playback system 506 may be configured to proceedwith playing the first media item if no transmission indicating thecontrary is received within a predetermine period of time.

At block 658, the method 650 involves sending to the service provider, atransmission indicating a request for a second media item. Continuingwith the examples above, the media playback system 506 may send atransmission to the service provider 502 requesting a different, secondmedia item to be played. In one example, the transmission may indicateone or more user accounts and/or preference data indicating why thefirst media item is not to be played and why the second media item isrequested.

FIG. 6C shows an example flow diagram of a method 670 for an embodimentin which the service provider 502 provides the different media itembased on the received transmission. Method 670 shown in FIG. 6C presentsan embodiment of a method that can be implemented within an operatingenvironment involving, for example, the media playback system 100 ofFIG. 1, one or more of the playback device 200 of FIG. 2, one or more ofthe control device 300 of FIG. 3, and the media playback systemenvironment 500 of FIG. 5. In other words, the method 650 may beperformed by any one or more of the devices, systems, and serversdescribed above. Method 650 may include one or more operations,functions, or actions as illustrated by one or more of blocks 652-658.Although the blocks are illustrated in sequential order, these blocksmay also be performed in parallel, and/or in a different order thanthose described herein. Also, the various blocks may be combined intofewer blocks, divided into additional blocks, and/or removed based uponthe desired implementation.

At block 672, the method 670 involves providing to a media playbacksystem, a first media item to be played. Continuing with the aboveexample, the first media item may be the media item provided to themedia playback system 506 as identified by the media data of block 606,in connection to FIG. 6A.

At block 674, the method 670 involves receiving a transmissionindicating the first media item is not to be played. The transmissionmay be the transmission indicating a request for a different media itemas provided by the media playback system 506 at block 658 of FIG. 6B, orthe transmission provided by the media system server 504 at block 612 ofFIG. 6A. In addition, the transmission may include the identification ofan additional user account(s) that is interfacing with the mediaplayback system 506.

At block 676, the method 670 involves identifying a second media itembased on the received transmission. In one case, the service provider502 may identify the second media item based on the input and/or mediapreferences (associated with the first user account 508, for example)that caused the service provider 502 to identify the first media itemthat was previously provided to the media playback system 506. Inanother case, if the received transmission identifies an additional useraccount that is interfacing with the media playback system 506, theservice provider 502 may identify the second media item based at leastpartially on the profile of the additional user account in addition tothe profile of the first user account (similar to the method 680discussed below).

Block 678 of method 670 involves sending to the media playback system,the second media item to be played. The service provider 502 may sendthe second media item to the media playback system 506 for playback. Insome cases, the service provider 502, if in communication with the mediasystem server 504, may send to the media system server 504, media dataidentifying the second media item. Other examples are also possible.

FIG. 6D shows an example flow diagram of a method 680 for an embodimentin which the service provider 502 provides the media items based on theprofiles of a plurality of user accounts interfacing with the mediaplayback system 506. Method 680 shown in FIG. 6D presents an embodimentof a method that can be implemented within an operating environmentinvolving, for example, the media playback system 100 of FIG. 1, one ormore of the playback device 200 of FIG. 2, one or more of the controldevice 300 of FIG. 3, and the media playback environment 500 of FIG. 5.In other words, the method 680 may be performed by any one or more ofthe devices, systems, and servers described above. In one example, thefunctions discussed in relation to the method 680 may be performed byone the service provider 502. Method 680 may include one or moreoperations, functions, or actions as illustrated by one or more ofblocks 682-686. Although the blocks are illustrated in sequential order,these blocks may also be performed in parallel, and/or in a differentorder than those described herein. Also, the various blocks may becombined into fewer blocks, divided into additional blocks, and/orremoved based upon the desired implementation.

At block 682, the method 680 involves receiving a transmissionidentifying a plurality of user accounts interfacing with a mediaplayback system. The plurality of user accounts may be the user accountsthat are currently interfacing with the media playback system 506.

At block 684, the method 680 involves identifying one or more mediaitems based on the preferences the plurality of user accounts. As oneexample, the service provider 502 may analyze the preferences of theidentified user accounts, and based on those preferences, identify mediacontent. Continuing with the example, if each of the preferences of theidentified user accounts indicate a preference for smooth jazz music,the sever provider 502 may identify a smooth jazz song. In anotherexample, the media items may be identified by ignoring a media item thathas a negative preference associated with any of the plurality of useraccounts.

In some cases, identifying common preferences between profiles may bedifficult, for example, if there are a large number of users currentlyinterfacing with the system. In such a situation, media items may beidentified based on the most common preference amongst the plurality ofusers. As another example, the media item that has the most number of“likes” (or any other form of positive preference) across the pluralityof user accounts may be identified, regardless of whether one of theplurality of user accounts has a negative preference associated with themedia item.

As another example, a cumulative preference percentage for the mediaitem may be determined. The cumulative preference percentage of themedia item may be determined as a percentage of the identified useraccounts that have a negative preference associated with the media itemsubtracted from a percentage of the identified user accounts that have apositive preference associated with the media item. As such, if eightout of 10 identified user accounts have a positive preference associatedwith the particular genre of music, but the remaining two identifieduser accounts have a negative preference associated with the particulargenre of music, the cumulative preference percentage may be 80%-20%=60%.In such a case, a media item with the highest cumulative preferencepercentage may be selected.

As yet another example, songs may be identified for each of the useraccounts interfacing with the media playback system, identifying songsbased on the preferences of that account. If any of the identified songsare common between the profiles, they can be selected for transmission.Other examples are possible as well.

At block 686, the method 680 involves providing the identified one ormore media items to the media playback system. Continuing with theexamples above, the one or more media items may be provided to the mediaplayback system 506. In addition to providing the media item(s),metadata indicating why the item(s) was selected may also be included.For example, the metadata could identify characteristics common to thepreferences of the plurality of user accounts. Providing such metadatawill allow users of the media playback system to understand why themedia items were selected.

One having ordinary skill in the art will appreciate the method 680 asdescribed above provides just one example of a service provideridentifying media content based on media preferences of multiple users.Other examples are also possible.

In addition, one having ordinary skill in the art will appreciate thatthe examples discussed above may be applied in various media playbackscenarios. For instance, the embodiments described herein may generallybe applied to a scenario in which the service provider 502 providesmedia items that were requested, but not specifically chosen using thefirst user account 508 (i.e. a selection of a catered playlist, or aradio channel, among others). On the other hand, if the first useraccount 508 was used to explicitly and specifically select a media item,the media item may be played by the media playback system, whether anypreference, positive or negative is identified. In such a case, theprocess of identifying a preference associated with the second useraccount 510 may be simply bypassed. Alternatively, an indication thatthe media item was explicitly and specifically selected using the firstuser account 508 may override any preferences associated with the seconduser account 510 when determining whether the media item should beplayed. In addition to the scenarios described above, embodiments hereinmay also be implemented and/or applied in other media playback scenariosto achieve similar or difference purposes as well, such as a parentalcontrol of media content. Other examples are also possible.

IV. Conclusion

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

As indicated above, the examples provided herein involve managingplayback of media content by a media playback system based on identifiedpreference data associated with one of a plurality of user accountsinterfacing with the media playback system. In one embodiment, a methodis provided. The method involves maintaining, by a computing device, aplurality of user accounts associated with a media playback system, themedia playback system comprising at least one playback device,receiving, by the computing device, user data identifying which of theplurality of user accounts are currently interfacing with the mediaplayback system, receiving, by the computing device, media dataidentifying a media item to be played by the media playback system,identifying, by the computing device, for at least one of the pluralityof user accounts that are currently interfacing with the media playbacksystem, preference data associated with the media item, and determining,by the computing device, that the media item is not to be played by amedia playback system, based on the identified preference data.

In another embodiment, a device is provided. The device includes aprocessor, and memory having stored thereon instructions executable bythe processor to cause the device to perform functions. The functionsinclude maintaining a plurality of user accounts associated with a mediaplayback system, the media playback system comprising at least oneplayback device, receiving user data identifying which of the pluralityof user accounts are currently interfacing with the media playbacksystem, receiving media data identifying a media item to be played bythe media playback system, identifying for at least one of the pluralityof user accounts that are currently interfacing with the media playbacksystem, preference data associated with the media item, and determiningthat the media item is not to be played by a media playback system,based on the identified preference data.

In yet another embodiment, a non-transitory computer readable memory isprovided. The non-transitory computer readable memory has stored thereoninstructions executable by a computing device to cause the computingdevice to perform functions. The functions include maintaining aplurality of user accounts associated with a media playback system, themedia playback system comprising at least one playback device, receivinguser data identifying which of the plurality of user accounts arecurrently interfacing with the media playback system, receiving mediadata identifying a media item to be played by the media playback system,identifying for at least one of the plurality of user accounts that arecurrently interfacing with the media playback system, preference dataassociated with the media item, and determining that the media item isnot to be played by a media playback system, based on the identifiedpreference data.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of aninvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

I claim:
 1. A playback device of a media playback system comprising: anetwork interface; one or more processors; and tangible, non-transitorycomputer-readable media having stored thereon instructions that, whenexecuted by the one or more processors, cause the playback device toperform functions comprising: receiving, via the network interface froma first control device of the media playback system, an instruction toqueue a container of audio tracks into a queue for playback by theplayback device, wherein the container of audio tracks consists of: (a)an album, (b) a playlist, or (c) an internet radio station; receiving,via the network interface from the first control device or a secondcontrol device of the media playback system, an instruction to queue aparticular audio track into the queue for playback by the playbackdevice, wherein the particular audio track is associated with a negativepreference; while the playback device is playing back the queue via oneor more speakers and before each audio track of the container is playedback, determining whether the respective audio track is associated witha negative preference; when the respective audio track is associatedwith the negative preference, advancing playback over the respectiveaudio track to the next audio track within the queue; and when a givenaudio track in the queue was individually added to the queue, playingback the given audio track regardless of whether any negative preferenceis associated with the given audio track.
 2. The playback device ofclaim 1, wherein playing back the given audio track regardless ofwhether any negative preference is associated with the given audio trackcomprises: receiving, via the network interface from the first controldevice or a second control device of the media playback system, aninstruction to queue a particular audio track into the queue forplayback by the playback device; before the particular audio track isplayed back, determining that the particular audio track is associatedwith the negative preference; and overriding the negative preferenceassociated with the particular audio track based on the particular audiotrack being queued individually in the queue such that the particularaudio track is played back regardless of the associated negativepreference.
 3. The playback device of claim 1, wherein determiningwhether the audio track is associated with the negative preferencecomprises: identifying one or more user accounts currently interfacingwith the playback device via the network interface; transmitting, viathe network interface to a media system server, a first messageindicating (i) the respective audio track and (ii) the identified one ormore user accounts; and receiving, via the network interface from themedia system server in response to the first message, a second messageindicating that the respective audio track is associated with thenegative preference.
 4. The playback device of claim 1, wherein thefirst control device is associated with a first user account, andwherein determining whether the audio track is associated with thenegative preference comprises: transmitting, via the network interfaceto a media system server, a first message indicating (i) the respectiveaudio track and (ii) the first user account; and receiving, via thenetwork interface from the media system server in response to the firstmessage, a second message indicating that the respective audio track isassociated with the negative preference.
 5. The playback device of claim1, wherein the container of audio tracks is associated with a streamingaudio service, and wherein determining whether the audio track isassociated with the negative preference comprises: identifying one ormore user accounts of the streaming audio service registered to themedia playback system; transmitting, via the network interface to aserver of the streaming audio service, a first message indicating (i)the respective audio track and (ii) the identified one or more useraccounts of the streaming audio service; and receiving, via the networkinterface from the server of the streaming audio service in response tothe first message, a second message indicating that the respective audiotrack is associated with the negative preference.
 6. The playback deviceof claim 5, wherein the playback device playing back the queue comprisesthe playback device streaming the audio tracks of the container from oneor more servers of the streaming audio service according to playbacksequence defined by the container.
 7. The playback device of claim 1,wherein the functions further comprise: in response to advancingplayback over the respective audio track to the next audio track withinthe queue, transmitting, to the first control device, one or more statevariables indicating the currently playing audio track.
 8. Tangible,non-transitory computer-readable media having stored thereoninstructions that, when executed by one or more processors of a playbackdevice, cause the playback device to perform functions comprising:receiving, via a network interface from a first control device of amedia playback system, an instruction to queue a container of audiotracks into a queue for playback by the playback device, wherein thecontainer of audio tracks consists of: (a) an album, (b) a playlist, or(c) an internet radio station; receiving, via the network interface fromthe first control device or a second control device of the mediaplayback system, an instruction to queue a particular audio track intothe queue for playback by the playback device, wherein the particularaudio track is associated with a negative preference; while the playbackdevice is playing back the queue via one or more speakers and beforeeach audio track of the container is played back, determining whetherthe respective audio track is associated with a negative preference;when the respective audio track is associated with the negativepreference, advancing playback over the respective audio track to thenext audio track within the queue; and when a given audio track in thequeue was individually added to the queue, playing back the given audiotrack regardless of whether any negative preference is associated withthe given audio track.
 9. The tangible, non-transitory computer-readablemedia of claim 8, wherein playing back the given audio track regardlessof whether any negative preference is associated with the given audiotrack comprises: receiving, via the network interface from the firstcontrol device or a second control device of the media playback system,an instruction to queue a particular audio track into the queue forplayback by the playback device; before the particular audio track isplayed back, determining that the particular audio track is associatedwith the negative preference; and overriding the negative preferenceassociated with the particular audio track based on the particular audiotrack being queued individually in the queue such that the particularaudio track is played back regardless of the associated negativepreference.
 10. The tangible, non-transitory computer-readable media ofclaim 8, wherein determining whether the audio track is associated withthe negative preference comprises: identifying one or more user accountscurrently interfacing with the playback device via the networkinterface; transmitting, via the network interface to a media systemserver, a first message indicating (i) the respective audio track and(ii) the identified one or more user accounts; and receiving, via thenetwork interface from the media system server in response to the firstmessage, a second message indicating that the respective audio track isassociated with the negative preference.
 11. The tangible,non-transitory computer-readable media of claim 8, wherein the firstcontrol device is associated with a first user account, and whereindetermining whether the audio track is associated with the negativepreference comprises: transmitting, via the network interface to a mediasystem server, a first message indicating (i) the respective audio trackand (ii) the first user account; and receiving, via the networkinterface from the media system server in response to the first message,a second message indicating that the respective audio track isassociated with the negative preference.
 12. The tangible,non-transitory computer-readable media of claim 8, wherein the containerof audio tracks is associated with a streaming audio service, andwherein determining whether the audio track is associated with thenegative preference comprises: identifying one or more user accounts ofthe streaming audio service registered to the media playback system;transmitting, via the network interface to a server of the streamingaudio service, a first message indicating (i) the respective audio trackand (ii) the identified one or more user accounts of the streaming audioservice; and receiving, via the network interface from the server of thestreaming audio service in response to the first message, a secondmessage indicating that the respective audio track is associated withthe negative preference.
 13. The tangible, non-transitorycomputer-readable media of claim 12, wherein the playback device playingback the queue comprises the playback device streaming the audio tracksof the container from one or more servers of the streaming audio serviceaccording to playback sequence defined by the container.
 14. Thetangible, non-transitory computer-readable media of claim 8, wherein thefunctions further comprise: in response to advancing playback over therespective audio track to the next audio track within the queue,transmitting, to the first control device, one or more state variablesindicating the currently playing audio track.
 15. A method to beperformed by a playback device, the method comprising: receiving, via anetwork interface of the playback device from a first control device ofa media playback system, an instruction to queue a container of audiotracks into a queue for playback by the playback device, wherein thecontainer of audio tracks consists of: (a) an album, (b) a playlist, or(c) an internet radio station; receiving, via the network interface fromthe first control device or a second control device of the mediaplayback system, an instruction to queue a particular audio track intothe queue for playback by the playback device, wherein the particularaudio track is associated with a negative preference; while the playbackdevice is playing back the queue via one or more speakers and beforeeach audio track of the container is played back, determining whetherthe respective audio track is associated with a negative preference;when the respective audio track is associated with the negativepreference, advancing playback over the respective audio track to thenext audio track within the queue; and when a given audio track in thequeue was individually added to the queue, playing back the given audiotrack regardless of whether any negative preference is associated withthe given audio track.
 16. The method of claim 15, wherein playing backthe given audio track regardless of whether any negative preference isassociated with the given audio track comprises: receiving, via thenetwork interface from a control device of the media playback system, aninstruction to queue a particular audio track into the queue forplayback by the playback device; before the particular audio track isplayed back, determining that the particular audio track is associatedwith the negative preference; and overriding the negative preferenceassociated with the particular audio track based on the particular audiotrack being queued individually in the queue such that the particularaudio track is played back regardless of the associated negativepreference.
 17. The method of claim 15, wherein determining whether theaudio track is associated with the negative preference comprises:identifying one or more user accounts currently interfacing with theplayback device via the network interface; transmitting, via the networkinterface to a media system server, a first message indicating (i) therespective audio track and (ii) the identified one or more useraccounts; and receiving, via the network interface from the media systemserver in response to the first message, a second message indicatingthat the respective audio track is associated with the negativepreference.
 18. The method of claim 15, wherein the first control deviceis associated with a first user account, and wherein determining whetherthe audio track is associated with the negative preference comprises:transmitting, via the network interface to a media system server, afirst message indicating (i) the respective audio track and (ii) thefirst user account; and receiving, via the network interface from themedia system server in response to the first message, a second messageindicating that the respective audio track is associated with thenegative preference.
 19. The method of claim 15, wherein the containerof audio tracks is associated with a streaming audio service, andwherein determining whether the audio track is associated with thenegative preference comprises: identifying one or more user accounts ofthe streaming audio service registered to the media playback system;transmitting, via the network interface to a server of the streamingaudio service, a first message indicating (i) the respective audio trackand (ii) the identified one or more user accounts of the streaming audioservice; and receiving, via the network interface from the server of thestreaming audio service in response to the first message, a secondmessage indicating that the respective audio track is associated withthe negative preference.
 20. The method of claim 19, wherein theplayback device playing back the queue comprises the playback devicestreaming the audio tracks of the container from one or more servers ofthe streaming audio service according to playback sequence defined bythe container.